home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Magnum One
/
Magnum One (Mid-American Digital) (Disc Manufacturing).iso
/
d8
/
pcz31190.arc
/
PCZ.DOC
< prev
next >
Wrap
Text File
|
1990-09-29
|
15KB
|
388 lines
PCZ 3.09.90 August 16, 1990
PCZ - A Public Domain implementation
Zmodem, Ymodem, Xmodem, Xmodem-1K, Sealink
for the IBM PC family
PcConnect Zmodem by Drue Kennon and Gary Smith
PCZ is a public domain Zmodem implementation that will allow
users of communication software that does not implement internal
Zmodem to access it through an external program. It is a
fully-featured version of Zmodem, but does not have the large
volume of options provides by Omen Tech's DSZ. However,
I do believe that it will be suitable for the average BBS'r.
PCZ provides support for the basic Xmodem variants:
Xmodem, Xmodem-1K, Ymodem Batch & SEAlink.
The following is a description of how to start PCZ for file transfers.
LEGEND
Data enclosed in "[" "]" is optional.
Data enclosed in "<" ">" is required.
Command line:
Send
PCZ [PORT] <1-8> [SPEED] <300-19200> [f] <sz> [r] [@]<filenames.ext>
Recv
PCZ [PORT] <1-8> [SPEED] <300-19200> [f] <rz> [r] <filename.ext>
Ref:
port - the word "PORT"
1-8 - the number 1 - 8
speed - the word "SPEED"
300-19200 - the number 300, 1200, 2400 etc...
f - enable FOSSIL driver routines
*z - transfer type command e.g. sz, rz, sx, rx etc...
r - resume/recover aborted transfer (zmodem only)
@ - cmdfile transfer alert flag
filename.ext file name w/extension
Due to the nature of the beast, no support is provided for a default port &
no default port speed is assumed.
I personally never enter "port" or "speed", but always enter
their values. i.e. pcz 1 9600 f sz xxxxxxx.xxx The batch files
included reflect this method.
"ZMODEM BATCH RECEIVE"
To receive file(s) using Zmodem simply enter :
|-- PCZ 1 9600 rz - Using com port one, assume sender names.
batch | PCZ 2 300 rz - Using com port two. """
modes | PCZ 3 2400 rz - Using com port three at 2400 baud. """
|-- PCZ 4 1200 rz - Using com port four at 1200 baud. """
one file mode:
PCZ 1 9600 rz INFILE.ARC - Receives one file and names it INFILE.ARC
PCZ 1 9600 rz r INFILE.ARC - Recovery xfer effort on file INFILE.ARC
"ZMODEM SEND"
To send one file using Zmodem simply enter :
PCZ 1 300 sz OUTFILE.ARC - Using com port one at 300 baud.
PCZ 2 2400 sz OUTFILE.ARC - Using com port two at 2400 baud
PCZ 3 9600 sz OUTFILE.ARC - Using com port three at 9600 baud.
PCZ 4 1200 sz OUTFILE.ARC - Using com port four at 1200 baud.
PCZ 1 9600 sz r OUTFILE.ARC - Send file and resume aborted transfer.
"ZMODEM BATCH SENDING"
To send a batch of files via Zmodem :
Create a TEXT command file with one complete file spec. per
line, which includes drive and directory information for
each file that is not in PCZ's resident directory.
e.g. C:\MYDIR\THISFILE.ZIP
A maximum of 25 files is allowed.
Have no blank lines in the file and place the "@" symbol
as the first character of the filename. Pass it
to PCZ on the command line as follows:
PCZ 1 2400 sz @OUTFILE.TXT - Uses port 1 at 2400 baud.
What you name the command file is your business. It simply
must be a standard ASCII file with no software or printer
control codes present.
An alternative to creating the command file for sending
2 or 3 files may be used. Simply type the file names on the
dos command line seperating each one with a space.
Remember the receiver must be set to accept batch uploads
or you might be spinning your wheels. Some BBS packages
are just now comming online with batch upload features using
PCZ or DSZ. They normally indicate (BATCH) if acceptable.
"XMODEM VARIANTS"
To receive files using any of the Xmodem variants, the format is :
PCZ <port> <speed> rs filename - SEAlink recieve
PCZ <port> <speed> rs - SEAlink Batch recieve
PCZ <port> <speed> rx filename - Xmodem receive
PCZ <port> <speed> r1 filename - Xmodem-1K receive
PCZ <port> <speed> ry filename - Ymodem receive
PCZ <port> <speed> ry - Ymodem Batch receive
To send files using any of the Xmodem variants, the format is :
PCZ <port> <speed> sx filename - Xmodem
PCZ <port> <speed> s1 filename - Xmodem-1K
PCZ <port> <speed> sy filename - Ymodem *
PCZ <port> <speed> ss filename - SEAlink *
*Refer to Zmodem Batch sending for batch transfers via
Ymodem and SEAlink
"ENVIRONMENT VARIABLES"
PCZ supports several environment variables which can make setting up a
comm pkg or BBS more "user friendly". These variables are as follows and
should be placed in the autoexec.bat file as I have them shown here:
set DIRRX=drive:\yourdir\
set PCZLOG=drive:\yourdir\
drive = a letter "A" - "Z" etc... yourdir is the directory you want PCZ to
place all your downloaded files into. In the case of the log file, it
specifies the directory you want your pcz.log file kept in. If PCZLOG is
not found in the environment then no log file is generated. As an option to
the log file name "PCZ.LOG" you may specify a filename in the filespec. i.e.
set PCZLOG=C:\COMM\MYLOG.FIL
This provides greater flexibility with some bbs pkgs such as RBBS which likes
it's own names in a multitasking environment etc... If the filename.ext
exist, it overrides "PCZ.LOG" in all cases.
set PCZPORT=(1-8)
PCZ will use the port number (1-8) you specify as the default port.
set PCZSPEED=(300-19200)
PCZ will use the speed (300-19200) you specify as the default speed.
If you specify a PORT or SPEED on the command line, it will override
the default set by the environment variables.
IMPORTANT NOTE:
NO SPACES are allowed in the setting of an environment variable!
e.g.
set PCZLOG = C:\COMM\ will not work.
That's not my fault. It is just DOS....
Note: the bytes and cps rate reflect the actual number of bytes sent to,
or received from the IOBuffer. It does not necessarily reflect any specific
"BLOCKSIZE". This will let you see actually how PCZ is progressing in the
transmission of data. In the best case "Full Streaming Zmodem", you will
see the time for actual file data; worse case time will reflect the
transmission of data headers and block acks. It is different, but I hope
everyone can appreciate a more accurate account of what is happening inside
the powerful zmodem protocol.
** : The "Transfer Time" reflects port speed, NOT modem speed!
If speed conversion is being used, FORGET the transfer time.
"FOSSIL SUPPORT"
FOSSIL is an acronym for "Fido/Opus/SEAdog Standard Interface Layer".
This version of PCZ implements the use of FOSSIL communications support.
To date only one, "X00.SYS" has been tested to work with PCZ. X00.SYS
is a product of Raymond Gwinn. It has proven itself in many environments
and I recommend it to you without reservation. X00.SYS was chosen because
it provides support for the 16550 UART chip which my internal routines
don't, and for the enhanced ability to work in a multitasking environment
such as DeskView. If DeskView is active PCZ gives idle time back to the
processor for enhanced operation. For a brief description of setting up
X00.SYS on your system read the enclosed file PCZFOSSL.DOC
Making use of the driver is as simple as adding "f" to the command line.
It should be placed after the baudrate in all xfer types.
e.g.
PCZ 1 9600 f sz OUTFILE.ZIP
When PCZ starts, it will check for the presence of the driver in memory.
If it is resident all will proceed as planned. If however, the driver
is not in memory, PCZ will gracefully shut down with a message stating
this fact. I gave careful thought to jumping to the internal routines,
but decided against it for a couple of reasons. In some cases the ports
may be scrambled which will surely cause a system lockup on PCZ's part.
A problem may exist with the driver your using, giving false info which
PCZ's routines would not like very much. A "dumb" terminal might have
charge of things and not want another routine hanging around, etc...
"PHONE SUPPORT"
Phone support can be provided when you require it, if you call while
I am home. I umpire for our local women's softball league on Mon. &
Tues. nights. I play golf on Wed. & Thurs. evenings. Fri. night I
do what Maureen tells me to do! Sat. is up for grabs and Sun. morn &
evenings I am in church. Please try me sometime other than those
mentioned...... Seriously though, any night (late) will be fine. Just
try and make it before 10p.m. cst if possible.
Note from the author:
Over the last year PCZ has received some very good reviews. More
users rely on the program for their transfers now than I thought
would ever be interested. For this I am especially grateful and
would thank each one if possible. Gary & I will continue to grow
with the needs of the BBS community. We ask for your continued
input and support, with our assurance that your ideas and "jeers"
are taken with sincerity.
Thanks
Drue
History
-------
V1.01.88 - Intial release, no known bugs. Please report
any problems to Drue Kennon.
V2.01.89 - Extended version that contains Xmodem, Xmodem-1K,
Sealink, and Ymodem Batch in addition to Zmodem.
Also provides full file sharing for use in
networking enviroments.
V2.11.89
Fixed several reported bugs. Enabled hardware flow
control for use with MNP type modems. Enhanced port
speeds up to 19.2k, and tightened some code for
more efficient operation. Properly set errorlevel 1
in event of transfer failure.
V3.03.90
Fixed a problem with SEAlink xfers not seeing the
last EOT. Batch sending for SEAlink per request.
enhanced some screen data writes
V3.06.90
Fixed a problem with SEAlink xfers created by making
the last fix. Zmodem command file name can't be
fouled due to misunderstanding the docs.
NOTE: Unless forced into it by the users, I do
not plan to support 7 bit data transfers.
Nor can I figure why any BBS would? Did
I misssssy something along the way?
V3.08.90
Got with the program and added support for FOSSIL
driver. e.g. Gwinn's Communications Controller,
X00.SYS (add "f" to cmd line params for fossil).
Removed internal support for default port and speed
which caused problems for multitaskers. Defaults
are now specified through environment variables.
Added environment variable for default receive dir.
Reinstated environment variable for pcz log file.
V3.09.90
By popular demand, namely "Gary", I added yet another
multitasker enhancement. Since the cpu is much faster
than the port, idle time occurs during output. This
time is now "given back" to the cpu, allowing the
"other side" to operate more efficiently.
V3.10.90
Some users mentioned that PCZ would wait forever in a
transfer if the carrier was lost. I couldn't dupe the
problem, but added several more checks nonetheless. The
logfile has changed so that you may specify a full file
spec. including filename for you logfile in the env. var.
The first char of each line in the file represents pass
or fail. "0" = failed xfer "1" = good xfer. Keep those
cards and letters coming!
Contact may be made by any one of the following methods.
Drue Kennon Gary J. Smith
Rural Route #2 Box 54 6122 Cedar Wood Drive
Center, TX. 75935 Columbia, MD 21044
Voice 409-598-3809
The Programmer's Corner
Home of
"PcConnect" BBS Software & "PCZ"
Data/BBS: 301-596-1180 Data/BBS: 301-995-3744
6 roll over lines in place
with over 3/4 gigabyte of
storage space
For use by corporations, government, institutions, or for
profit, contact Omen Technology Incorporated for licensing
information using their excellent commercialized Zmodem
implementation. i.e. "DSZ"
Chuck Forsberg
Omen Technology Inc
The High Reliability Software
17505-V Northwest Sauvie Island Road
Portland Oregon 97231
Modem: 503-621-3746 Speed 1200,2400,19200(Telebit PEP)
Compuserve:70007,2304 GEnie:CAF
UUCP: ...!tektronix!reed!omen!caf
Omen Technolgy makes Professional-YAM, a comphrensive comms program with
unmatched power. Flavors are available for PC-DOS, Unix, Xenix, and OS/2
Protected mode.
ZCOMM is a full featured shareware communications package.
DSZ, ZCOMM, Professional-YAM
are Copyrights of Omen Technology Inc, all rights reserved.
X00.SYS Copyright (c) by Raymond L. Gwinn, All Rights Reserved
PCZ.EXE Copyright (c) by Drue Kennon, All Rights Reserved